Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 122433417de161190e831268f15a331d2c6783464d3191fef1f2700a3469036c

Tx prefix hash: 20ee75aad3b6617684c3386fa0b8be905f46019895c70df4dffe158bf9b9fd21
Tx public key: b631ee3fd96caef938e4a299b10ed43d8521434fadef7fce8f8c84e5b85df906
Timestamp: 1714817987 Timestamp [UCT]: 2024-05-04 10:19:47 Age [y:d:h:m:s]: 00:194:15:50:30
Block: 1014602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139321 RingCT/type: yes/0
Extra: 01b631ee3fd96caef938e4a299b10ed43d8521434fadef7fce8f8c84e5b85df9060211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38c5e4355212d9c6c0c87045c139cb23a8a01d70a7adfa68e5aaf3ccd29061d5 0.600000000000 1477739 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": 1014612, "vin": [ { "gen": { "height": 1014602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38c5e4355212d9c6c0c87045c139cb23a8a01d70a7adfa68e5aaf3ccd29061d5" } } ], "extra": [ 1, 182, 49, 238, 63, 217, 108, 174, 249, 56, 228, 162, 153, 177, 14, 212, 61, 133, 33, 67, 79, 173, 239, 127, 206, 143, 140, 132, 229, 184, 93, 249, 6, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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