Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213a6f9a6bde8d1c1de8841fabe1b3b1a040a5fba03da6ca431e74980b03b8ab

Tx prefix hash: 579b1bb092cfed93297a82d16e41bfef574706639cfafb408b88ab3811a2159f
Tx public key: 1abcef0b618197544c470a5263433ae03e20febc72fb26336f53bbb254c54a65
Timestamp: 1702635818 Timestamp [UCT]: 2023-12-15 10:23:38 Age [y:d:h:m:s]: 01:184:21:10:44
Block: 913592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393209 RingCT/type: yes/0
Extra: 011abcef0b618197544c470a5263433ae03e20febc72fb26336f53bbb254c54a65021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c609c49408cfe324c8c61ad642c6d6aef2d8a21cb7f7c944cfc2905b8a387c0 0.600000000000 1370866 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": 913602, "vin": [ { "gen": { "height": 913592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c609c49408cfe324c8c61ad642c6d6aef2d8a21cb7f7c944cfc2905b8a387c0" } } ], "extra": [ 1, 26, 188, 239, 11, 97, 129, 151, 84, 76, 71, 10, 82, 99, 67, 58, 224, 62, 32, 254, 188, 114, 251, 38, 51, 111, 83, 187, 178, 84, 197, 74, 101, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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