Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e0d1ef37f5bee9b9386fd40aed47f8da457f669b0da994366a31df4f731b28

Tx prefix hash: b2242528e5174b837ac1a0547d00f8cf3c221c0aa4a909c6a3ff793ef1faedbe
Tx public key: bb21fe18ce4f1b91769411b29d93ada6d5fec6abc291299777cbef89d73eb8b5
Timestamp: 1716004775 Timestamp [UCT]: 2024-05-18 03:59:35 Age [y:d:h:m:s]: 01:009:15:12:14
Block: 1024431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267806 RingCT/type: yes/0
Extra: 01bb21fe18ce4f1b91769411b29d93ada6d5fec6abc291299777cbef89d73eb8b502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 678e2e4e3a0c20f3f9ac5e4b59fc39201f6bc25af6ed04d7f4aaafb7a34c60d2 0.600000000000 1490176 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": 1024441, "vin": [ { "gen": { "height": 1024431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "678e2e4e3a0c20f3f9ac5e4b59fc39201f6bc25af6ed04d7f4aaafb7a34c60d2" } } ], "extra": [ 1, 187, 33, 254, 24, 206, 79, 27, 145, 118, 148, 17, 178, 157, 147, 173, 166, 213, 254, 198, 171, 194, 145, 41, 151, 119, 203, 239, 137, 215, 62, 184, 181, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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