Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7cee85892fdbe3a8e203ec0d78365043e9c4c3a8b564b27c327e63d896b201b

Tx prefix hash: 26bef78b549ee7d84b0ef2d7a984d3b0fef31e8ac84d521d20762760288b30f5
Tx public key: 17f5c28c57ee296847683d52bfc89e9e47b56a371fd354f5b1da8b2052a33034
Timestamp: 1725072705 Timestamp [UCT]: 2024-08-31 02:51:45 Age [y:d:h:m:s]: 00:217:11:55:36
Block: 1099608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155299 RingCT/type: yes/0
Extra: 0117f5c28c57ee296847683d52bfc89e9e47b56a371fd354f5b1da8b2052a33034021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc3449d4de623461548507566144b52313022d535b2951ddb6cca3a14199e3aa 0.600000000000 1575573 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": 1099618, "vin": [ { "gen": { "height": 1099608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc3449d4de623461548507566144b52313022d535b2951ddb6cca3a14199e3aa" } } ], "extra": [ 1, 23, 245, 194, 140, 87, 238, 41, 104, 71, 104, 61, 82, 191, 200, 158, 158, 71, 181, 106, 55, 31, 211, 84, 245, 177, 218, 139, 32, 82, 163, 48, 52, 2, 17, 0, 0, 0, 2, 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