Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5bfe2597305a60eaa808dfd8918f3822ef331d686ea7b554f3b323d84fd823f

Tx prefix hash: a3a3597d4cd11e3f6fc08df451388b10fcfa4efeb5cb0265b837615954655039
Tx public key: 4769c90e7d7e7eb692bb15c7b6bbdcd52366e297a899a1214f7a54638c10ac64
Timestamp: 1724680653 Timestamp [UCT]: 2024-08-26 13:57:33 Age [y:d:h:m:s]: 01:073:19:57:38
Block: 1096354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311222 RingCT/type: yes/0
Extra: 014769c90e7d7e7eb692bb15c7b6bbdcd52366e297a899a1214f7a54638c10ac64021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27c67abcc2a315429a8a21ae4ec08185d2ec656afdcaaa1101ce6e787160a9f1 0.600000000000 1571543 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": 1096364, "vin": [ { "gen": { "height": 1096354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27c67abcc2a315429a8a21ae4ec08185d2ec656afdcaaa1101ce6e787160a9f1" } } ], "extra": [ 1, 71, 105, 201, 14, 125, 126, 126, 182, 146, 187, 21, 199, 182, 187, 220, 213, 35, 102, 226, 151, 168, 153, 161, 33, 79, 122, 84, 99, 140, 16, 172, 100, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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