Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81cfaf761d35d4c275fdd3bd82dd46616b130437ab3958afbc9c755dce613342

Tx prefix hash: c8d872419b92ec78286ad2de727f8ad50fce93a3276a121fbfdc7913cc9afecb
Tx public key: f588f7c79c38336528366df1d2f0f1b2256aacb0d02ccfbb7edf9ee998fcc7d9
Timestamp: 1737802699 Timestamp [UCT]: 2025-01-25 10:58:19 Age [y:d:h:m:s]: 00:048:13:49:59
Block: 1204952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34537 RingCT/type: yes/0
Extra: 01f588f7c79c38336528366df1d2f0f1b2256aacb0d02ccfbb7edf9ee998fcc7d9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef668b7a2a312090980073986a5fc9ea4f0bef350e6eba81da293c7b2e92a292 0.600000000000 1691647 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": 1204962, "vin": [ { "gen": { "height": 1204952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef668b7a2a312090980073986a5fc9ea4f0bef350e6eba81da293c7b2e92a292" } } ], "extra": [ 1, 245, 136, 247, 199, 156, 56, 51, 101, 40, 54, 109, 241, 210, 240, 241, 178, 37, 106, 172, 176, 208, 44, 207, 187, 126, 223, 158, 233, 152, 252, 199, 217, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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