Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f415ef15921843f515d86bc355011556c5da2c24ac82ef2468cbfe9e19c175a

Tx prefix hash: eaaeef676b2d262c821f3d3ee08a165ef56b68990b75917e8f07f9e40d01bcfb
Tx public key: dd14c70af815181600a246b0d871991d1d204a105264ae56400df3522b8ee313
Timestamp: 1729307117 Timestamp [UCT]: 2024-10-19 03:05:17 Age [y:d:h:m:s]: 00:175:05:06:40
Block: 1134710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125009 RingCT/type: yes/0
Extra: 01dd14c70af815181600a246b0d871991d1d204a105264ae56400df3522b8ee3130211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 983cbb7792d80402d2a5c4e6917b5b5c88f7ab2a8092b0b975d18d9502bd53c4 0.600000000000 1618035 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": 1134720, "vin": [ { "gen": { "height": 1134710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "983cbb7792d80402d2a5c4e6917b5b5c88f7ab2a8092b0b975d18d9502bd53c4" } } ], "extra": [ 1, 221, 20, 199, 10, 248, 21, 24, 22, 0, 162, 70, 176, 216, 113, 153, 29, 29, 32, 74, 16, 82, 100, 174, 86, 64, 13, 243, 82, 43, 142, 227, 19, 2, 17, 0, 0, 0, 4, 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