Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c689396d9c71bb9b0a24c8150703836b968d16c8d0f8e24ac476a48fe0bf0265

Tx prefix hash: 27ce82533bb99f5c0e6459878c902e4d46d01df6ec493bd5f10c9ce487ec1218
Tx public key: c2d422e1eafbfeebd5817eff8525f36f3ea23424f92cfc76e668b405f589756f
Timestamp: 1723205843 Timestamp [UCT]: 2024-08-09 12:17:23 Age [y:d:h:m:s]: 00:136:23:58:37
Block: 1084134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98018 RingCT/type: yes/0
Extra: 01c2d422e1eafbfeebd5817eff8525f36f3ea23424f92cfc76e668b405f589756f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15ec1fb7cc3a3efb7877676e9db5f3227496e6e7d5723690da8b2503fc920527 0.600000000000 1558297 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": 1084144, "vin": [ { "gen": { "height": 1084134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15ec1fb7cc3a3efb7877676e9db5f3227496e6e7d5723690da8b2503fc920527" } } ], "extra": [ 1, 194, 212, 34, 225, 234, 251, 254, 235, 213, 129, 126, 255, 133, 37, 243, 111, 62, 162, 52, 36, 249, 44, 252, 118, 230, 104, 180, 5, 245, 137, 117, 111, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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