Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3833c7424e496d7a19521b60e0e40431d1fcbca06146cf2c7ba00e02c7d448

Tx prefix hash: b736abd861cc3da17cf06e91aaa79372f8042332647feaef80b797600de40199
Tx public key: a5c066c2e0c5a90da06bb05b9dd6882e16357b5afdf6b4e3ef7ea2a1ff0a695c
Timestamp: 1658805900 Timestamp [UCT]: 2022-07-26 03:25:00 Age [y:d:h:m:s]: 02:239:19:33:08
Block: 551854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692570 RingCT/type: yes/0
Extra: 01a5c066c2e0c5a90da06bb05b9dd6882e16357b5afdf6b4e3ef7ea2a1ff0a695c02110000000cf7dd2130000000000000000000

1 output(s) for total of 9.109168634000 dcy

stealth address amount amount idx
00: 060e101deb856df492500abf938edd8759838d0594844d43928312681e3fb853 9.109168634000 983500 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": 551864, "vin": [ { "gen": { "height": 551854 } } ], "vout": [ { "amount": 9109168634, "target": { "key": "060e101deb856df492500abf938edd8759838d0594844d43928312681e3fb853" } } ], "extra": [ 1, 165, 192, 102, 194, 224, 197, 169, 13, 160, 107, 176, 91, 157, 214, 136, 46, 22, 53, 123, 90, 253, 246, 180, 227, 239, 126, 162, 161, 255, 10, 105, 92, 2, 17, 0, 0, 0, 12, 247, 221, 33, 48, 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