Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe64a60e5177c3d9de52b34ff98387c23ed12ca80d8d25b32a3a7aca94ab457f

Tx prefix hash: fc073338c7ef3d7077bd7b4b55815f73a42302362c44e16bf326b0e1415f88b3
Tx public key: ea7e107b9ee16ae89f4444ed420694a08dcffe3e42209d137cca79b7ea08c56a
Timestamp: 1729862374 Timestamp [UCT]: 2024-10-25 13:19:34 Age [y:d:h:m:s]: 00:151:18:04:41
Block: 1139278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108244 RingCT/type: yes/0
Extra: 01ea7e107b9ee16ae89f4444ed420694a08dcffe3e42209d137cca79b7ea08c56a0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 318a3bfc5ceff7557918af81293d81821d061a339d909bcc0bd28e787b99a651 0.600000000000 1623063 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": 1139288, "vin": [ { "gen": { "height": 1139278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "318a3bfc5ceff7557918af81293d81821d061a339d909bcc0bd28e787b99a651" } } ], "extra": [ 1, 234, 126, 16, 123, 158, 225, 106, 232, 159, 68, 68, 237, 66, 6, 148, 160, 141, 207, 254, 62, 66, 32, 157, 19, 124, 202, 121, 183, 234, 8, 197, 106, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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