Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a033b9f2f2fa3bdf2b28687d67956966c6fab77410a25dcd7c26ca026ebfa62a

Tx prefix hash: 45ef9d159338673809df5fefa6f7badf3172fe23392712c0210f3911a4346097
Tx public key: b626da58474810c2081cff55a738ba6e658a011546dc58934c693dd0fdfe43b6
Timestamp: 1578156234 Timestamp [UCT]: 2020-01-04 16:43:54 Age [y:d:h:m:s]: 05:301:23:55:46
Block: 38657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1363396 RingCT/type: yes/0
Extra: 01b626da58474810c2081cff55a738ba6e658a011546dc58934c693dd0fdfe43b602110000000ad81c26c0000000000000000000

1 output(s) for total of 456.997854664000 dcy

stealth address amount amount idx
00: e675feb7bbfc51d7a4ce6e1d2bda7070be65dc52b5dfad5039aa6eaff13a06a3 456.997854664000 66065 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": 38667, "vin": [ { "gen": { "height": 38657 } } ], "vout": [ { "amount": 456997854664, "target": { "key": "e675feb7bbfc51d7a4ce6e1d2bda7070be65dc52b5dfad5039aa6eaff13a06a3" } } ], "extra": [ 1, 182, 38, 218, 88, 71, 72, 16, 194, 8, 28, 255, 85, 167, 56, 186, 110, 101, 138, 1, 21, 70, 220, 88, 147, 76, 105, 61, 208, 253, 254, 67, 182, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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