Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1c521dfe6b548b956ed3adcec8893a35a46d02cdff90e6017f1fdd2a202be09

Tx prefix hash: b2b1dd5bfcf0d9cff8ef69d300eb0f1321c4575fb529e601f62e0ad91e825aa3
Tx public key: 4a0e49b0c681bd4b3245b8751f7acdf04183ece359b8edca805ece4bf62be13e
Timestamp: 1705139958 Timestamp [UCT]: 2024-01-13 09:59:18 Age [y:d:h:m:s]: 01:133:04:39:17
Block: 934340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356342 RingCT/type: yes/0
Extra: 014a0e49b0c681bd4b3245b8751f7acdf04183ece359b8edca805ece4bf62be13e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc09196f2b83b7a794c924256f9089f3bf651ed5f256f0aef6614714c443030c 0.600000000000 1392346 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": 934350, "vin": [ { "gen": { "height": 934340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc09196f2b83b7a794c924256f9089f3bf651ed5f256f0aef6614714c443030c" } } ], "extra": [ 1, 74, 14, 73, 176, 198, 129, 189, 75, 50, 69, 184, 117, 31, 122, 205, 240, 65, 131, 236, 227, 89, 184, 237, 202, 128, 94, 206, 75, 246, 43, 225, 62, 2, 17, 0, 0, 0, 5, 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