Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29ec2f4ce180fb02c3fa5262029ec7cdc56a138ede6d26a988708a480a724338

Tx prefix hash: e7086343d9f9d6a56df2f85899a07313213cd66ddd329c78dfd133c1eebbbe4d
Tx public key: 64c42823a8407f1afa25fefbb5b4ddc4c18345298d119a357bd523b1d99b81c6
Timestamp: 1699878425 Timestamp [UCT]: 2023-11-13 12:27:05 Age [y:d:h:m:s]: 01:185:16:46:49
Block: 890745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393919 RingCT/type: yes/0
Extra: 0164c42823a8407f1afa25fefbb5b4ddc4c18345298d119a357bd523b1d99b81c602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.686423346000 dcy

stealth address amount amount idx
00: 64a0aff977c73cc676f7c4ef0b1c412911a061ffec092b5e6108e8eb977325df 0.686423346000 1346776 of 0

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": 890755, "vin": [ { "gen": { "height": 890745 } } ], "vout": [ { "amount": 686423346, "target": { "key": "64a0aff977c73cc676f7c4ef0b1c412911a061ffec092b5e6108e8eb977325df" } } ], "extra": [ 1, 100, 196, 40, 35, 168, 64, 127, 26, 250, 37, 254, 251, 181, 180, 221, 196, 193, 131, 69, 41, 141, 17, 154, 53, 123, 213, 35, 177, 217, 155, 129, 198, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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