Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d706292aa8e41773803a81d632fed34ff9382cd1e1b0a742f1b1e17f969e61d9

Tx prefix hash: a10a008df2fdde96f022acbcc2302eaf871b640cf20c6bf50b5ec48a0bf51e33
Tx public key: 0f58c4febdd44eca3e4c95f3c03e23ab7ee4ed0a1541db6bf665418bdba04929
Timestamp: 1719147426 Timestamp [UCT]: 2024-06-23 12:57:06 Age [y:d:h:m:s]: 00:332:00:05:04
Block: 1050468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237305 RingCT/type: yes/0
Extra: 010f58c4febdd44eca3e4c95f3c03e23ab7ee4ed0a1541db6bf665418bdba049290211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b2b9fba1061776da3b2e2ad5af551b59a2df27e19d5f4e26172636a7441b877 0.600000000000 1520641 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": 1050478, "vin": [ { "gen": { "height": 1050468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b2b9fba1061776da3b2e2ad5af551b59a2df27e19d5f4e26172636a7441b877" } } ], "extra": [ 1, 15, 88, 196, 254, 189, 212, 78, 202, 62, 76, 149, 243, 192, 62, 35, 171, 126, 228, 237, 10, 21, 65, 219, 107, 246, 101, 65, 139, 219, 160, 73, 41, 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