Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 573dbe38ed5579682a36aa29b97ff3e7ccb1ca7ed2a8760caed0924a58e433e5

Tx prefix hash: 39779e75653bce4e0980b430bfc3a2aaecc20db210ec8d49fafe9bd7011c30f9
Tx public key: b244d11004b35d1f7213a75cd4ca4f24d5c0ebcaf140e40c8e0b7588568442c0
Timestamp: 1648025918 Timestamp [UCT]: 2022-03-23 08:58:38 Age [y:d:h:m:s]: 02:252:19:55:04
Block: 464564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700193 RingCT/type: yes/0
Extra: 01b244d11004b35d1f7213a75cd4ca4f24d5c0ebcaf140e40c8e0b7588568442c002110000000cd3fcec30000000000000000000

1 output(s) for total of 17.729924072000 dcy

stealth address amount amount idx
00: 5628fe7575432baaa9b77e36870a1f622883480faed8f96ee5c31dde8a11f717 17.729924072000 882479 of 0

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": 464574, "vin": [ { "gen": { "height": 464564 } } ], "vout": [ { "amount": 17729924072, "target": { "key": "5628fe7575432baaa9b77e36870a1f622883480faed8f96ee5c31dde8a11f717" } } ], "extra": [ 1, 178, 68, 209, 16, 4, 179, 93, 31, 114, 19, 167, 92, 212, 202, 79, 36, 213, 192, 235, 202, 241, 64, 228, 12, 142, 11, 117, 136, 86, 132, 66, 192, 2, 17, 0, 0, 0, 12, 211, 252, 236, 48, 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