Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1123d5c29803225abe2fca6bb9f050dad4894f1a8ff9edb00dab5ff0c40dadfd

Tx prefix hash: 0d60f06b85e38a4ccd40688fa7b11706807aeade0ea4f9fb27d79944c3160261
Tx public key: 3095305e2d67e387c47a17280d06a2b81d5c7fb526a23d1b3eda30ea3ffc38ed
Timestamp: 1715177715 Timestamp [UCT]: 2024-05-08 14:15:15 Age [y:d:h:m:s]: 01:267:05:51:39
Block: 1017590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449531 RingCT/type: yes/0
Extra: 013095305e2d67e387c47a17280d06a2b81d5c7fb526a23d1b3eda30ea3ffc38ed0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e02b1a1992b35b811d93f4105a82691ffbe366ff8bff903d3821d25bacd9f72 0.600000000000 1481373 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": 1017600, "vin": [ { "gen": { "height": 1017590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e02b1a1992b35b811d93f4105a82691ffbe366ff8bff903d3821d25bacd9f72" } } ], "extra": [ 1, 48, 149, 48, 94, 45, 103, 227, 135, 196, 122, 23, 40, 13, 6, 162, 184, 29, 92, 127, 181, 38, 162, 61, 27, 62, 218, 48, 234, 63, 252, 56, 237, 2, 17, 0, 0, 0, 1, 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