Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 757e514ec1da5ae0ba844d6b2e126070856ae817cd2fc6ab34bcd1b214c4f3c4

Tx prefix hash: 4658869c661050496cbe831d909db92f53a1b811c99e192e0930d5493eee6df8
Tx public key: 70495ec4995e8c339be38d7cf802942ed978be9c7a38fbe194ab77e05b0867d1
Timestamp: 1674853505 Timestamp [UCT]: 2023-01-27 21:05:05 Age [y:d:h:m:s]: 01:350:11:11:30
Block: 684155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511456 RingCT/type: yes/0
Extra: 0170495ec4995e8c339be38d7cf802942ed978be9c7a38fbe194ab77e05b0867d10211000000027e406890000000000000000000

1 output(s) for total of 3.319788493000 dcy

stealth address amount amount idx
00: ce3b8dd71b8c0a5e30500d57f7d6b687a2f24c8aa1ddf33e1218dea703701ed9 3.319788493000 1126368 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": 684165, "vin": [ { "gen": { "height": 684155 } } ], "vout": [ { "amount": 3319788493, "target": { "key": "ce3b8dd71b8c0a5e30500d57f7d6b687a2f24c8aa1ddf33e1218dea703701ed9" } } ], "extra": [ 1, 112, 73, 94, 196, 153, 94, 140, 51, 155, 227, 141, 124, 248, 2, 148, 46, 217, 120, 190, 156, 122, 56, 251, 225, 148, 171, 119, 224, 91, 8, 103, 209, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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