Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d72b4487e7002d464e0403dcbad4ac1c2dbe4cbcc78ecc9ddb4c32097342f9b

Tx prefix hash: 4b295642bd2f9df6d15c5562141d46f4badb1a943a3828526357379e6f2ddd9d
Tx public key: ce97fbabb743c129b9445fca688e11cdbd5922f6de32f35820be40f91e1d819b
Timestamp: 1701286212 Timestamp [UCT]: 2023-11-29 19:30:12 Age [y:d:h:m:s]: 01:149:02:36:50
Block: 902396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367755 RingCT/type: yes/0
Extra: 01ce97fbabb743c129b9445fca688e11cdbd5922f6de32f35820be40f91e1d819b02110000000733af99f4000000000000000000

1 output(s) for total of 0.628040180000 dcy

stealth address amount amount idx
00: fccdb5b3a07097801ceb83526067e5f6ad81b0f88541f5b2325dc7cff2eccf8a 0.628040180000 1359035 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": 902406, "vin": [ { "gen": { "height": 902396 } } ], "vout": [ { "amount": 628040180, "target": { "key": "fccdb5b3a07097801ceb83526067e5f6ad81b0f88541f5b2325dc7cff2eccf8a" } } ], "extra": [ 1, 206, 151, 251, 171, 183, 67, 193, 41, 185, 68, 95, 202, 104, 142, 17, 205, 189, 89, 34, 246, 222, 50, 243, 88, 32, 190, 64, 249, 30, 29, 129, 155, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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