Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4a2e1d639958c5305f24abb8807152f887026ed6e66459a0d7588e45333180

Tx prefix hash: 4d7d39e524eb6a5044b161e612bed874fb5e6b1a21297546e42b068de3f2b519
Tx public key: 26ccffc399222a22b4e977959d3379ecf5e34f3e1445a0cf600be9b9d08fc911
Timestamp: 1711452076 Timestamp [UCT]: 2024-03-26 11:21:16 Age [y:d:h:m:s]: 01:022:22:49:56
Block: 986715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277359 RingCT/type: yes/0
Extra: 0126ccffc399222a22b4e977959d3379ecf5e34f3e1445a0cf600be9b9d08fc9110211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae451f8e4ac50d473293ba155c6ba902b5a1847b95d0ad94f002e9f51217afc 0.600000000000 1446948 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": 986725, "vin": [ { "gen": { "height": 986715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae451f8e4ac50d473293ba155c6ba902b5a1847b95d0ad94f002e9f51217afc" } } ], "extra": [ 1, 38, 204, 255, 195, 153, 34, 42, 34, 180, 233, 119, 149, 157, 51, 121, 236, 245, 227, 79, 62, 20, 69, 160, 207, 96, 11, 233, 185, 208, 143, 201, 17, 2, 17, 0, 0, 0, 9, 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