Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3eaa00ff28e12cf8d6b003fb71b666fb22128c2ce6088f53bdefdf69e71c24e

Tx prefix hash: 7a02faadd8b5235d35e0fc1d6c142819c579228ae6df9fd7b8525fa06f954a03
Tx public key: 01f6b9959fb5c24e16863e961671d1a22ca73bbaef47e98b28ec66b04ad64330
Timestamp: 1731940700 Timestamp [UCT]: 2024-11-18 14:38:20 Age [y:d:h:m:s]: 01:002:15:56:22
Block: 1156450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260313 RingCT/type: yes/0
Extra: 0101f6b9959fb5c24e16863e961671d1a22ca73bbaef47e98b28ec66b04ad64330021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3c284557abc90ea5a3fe444b95dfa123fcd21866e041f8a92a05aa3b81951b4 0.600000000000 1642073 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": 1156460, "vin": [ { "gen": { "height": 1156450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3c284557abc90ea5a3fe444b95dfa123fcd21866e041f8a92a05aa3b81951b4" } } ], "extra": [ 1, 1, 246, 185, 149, 159, 181, 194, 78, 22, 134, 62, 150, 22, 113, 209, 162, 44, 167, 59, 186, 239, 71, 233, 139, 40, 236, 102, 176, 74, 214, 67, 48, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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