Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4771628fb952e6e7faeb2cba8b9e35fc030c2d5c8f710c4f42ee27e6851fb97d

Tx prefix hash: 75da8007eda9c4041c4ccdf704fb8790ffc7168b1717e524cc2f35ed53ec2a9f
Tx public key: 7ec0cd1fd90f896289d90128467dc604fc099b301c5819c659d98614c8b58917
Timestamp: 1730682844 Timestamp [UCT]: 2024-11-04 01:14:04 Age [y:d:h:m:s]: 00:078:22:42:03
Block: 1146045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56433 RingCT/type: yes/0
Extra: 017ec0cd1fd90f896289d90128467dc604fc099b301c5819c659d98614c8b5891702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45e5b524a8e229cfea70e1958d4f0c2b74cf90ad41283832bdfe7e6c5fe56f1c 0.600000000000 1630600 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1146055, "vin": [ { "gen": { "height": 1146045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45e5b524a8e229cfea70e1958d4f0c2b74cf90ad41283832bdfe7e6c5fe56f1c" } } ], "extra": [ 1, 126, 192, 205, 31, 217, 15, 137, 98, 137, 217, 1, 40, 70, 125, 198, 4, 252, 9, 155, 48, 28, 88, 25, 198, 89, 217, 134, 20, 200, 181, 137, 23, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8