Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05685d842353e273991712169a8c216020c727725ef87a14cfdc3775e444d78d

Tx prefix hash: fc5f7e0d04b6d2d3f15a76d41271f496b4c634efe95e76eb5a367e552d47750e
Tx public key: 235b3a97aae48321a8cba68a6885f49bb7feea474bdc73c5a29fbfb8cecc47dd
Timestamp: 1577168452 Timestamp [UCT]: 2019-12-24 06:20:52 Age [y:d:h:m:s]: 05:072:14:54:42
Block: 30438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201779 RingCT/type: yes/0
Extra: 01235b3a97aae48321a8cba68a6885f49bb7feea474bdc73c5a29fbfb8cecc47dd02110000000f4ac5aa02000000000000000000

1 output(s) for total of 486.572020818000 dcy

stealth address amount amount idx
00: 22057963a024805d766fe8fb0246d3a15379ccf06bd6afec02440d99a0495d1f 486.572020818000 50260 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": 30448, "vin": [ { "gen": { "height": 30438 } } ], "vout": [ { "amount": 486572020818, "target": { "key": "22057963a024805d766fe8fb0246d3a15379ccf06bd6afec02440d99a0495d1f" } } ], "extra": [ 1, 35, 91, 58, 151, 170, 228, 131, 33, 168, 203, 166, 138, 104, 133, 244, 155, 183, 254, 234, 71, 75, 220, 115, 197, 162, 159, 191, 184, 206, 204, 71, 221, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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