Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e4d7b792df6695cefc2f31ca6b7d7f915b32045c70f9fc2ea719dac8d7d7e0

Tx prefix hash: 015c97be40b7fb1103d385b90abac394f2a7ca5d9af3e4c271cd175fd69b0dca
Tx public key: 2e6f57c4503c5a49b4678c20f2d356357f760f0b7a2d8382536aaab4a9d20c2e
Timestamp: 1702674039 Timestamp [UCT]: 2023-12-15 21:00:39 Age [y:d:h:m:s]: 02:007:02:43:03
Block: 913914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524857 RingCT/type: yes/0
Extra: 012e6f57c4503c5a49b4678c20f2d356357f760f0b7a2d8382536aaab4a9d20c2e02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eed87a102db30b2595049e460fdbe8617bb611c173d4eecfafeef098ed64586 0.600000000000 1371194 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": 913924, "vin": [ { "gen": { "height": 913914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eed87a102db30b2595049e460fdbe8617bb611c173d4eecfafeef098ed64586" } } ], "extra": [ 1, 46, 111, 87, 196, 80, 60, 90, 73, 180, 103, 140, 32, 242, 211, 86, 53, 127, 118, 15, 11, 122, 45, 131, 130, 83, 106, 170, 180, 169, 210, 12, 46, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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