Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb4de849b1b1c92ec46bd1ab90d06e159c003878baffffe698be00c9f6c50a5

Tx prefix hash: 3e7a057c5734fee6b52f9a35d00c0ddab74a488c977551c1b996e2c7749ea2cd
Tx public key: 8dd37d8fcf06bb12b9ed778fcca63ab9367ade410a70db5a44dcdfc9af4db8e3
Timestamp: 1577990755 Timestamp [UCT]: 2020-01-02 18:45:55 Age [y:d:h:m:s]: 05:000:10:17:37
Block: 37376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150271 RingCT/type: yes/0
Extra: 018dd37d8fcf06bb12b9ed778fcca63ab9367ade410a70db5a44dcdfc9af4db8e302110000000c4ac5aa02000000000000000000

1 output(s) for total of 461.486124854000 dcy

stealth address amount amount idx
00: d06884cc67cd2ba3e61b015cd8389221d5ff7511beffef32ff5d7179c313d3a9 461.486124854000 63424 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": 37386, "vin": [ { "gen": { "height": 37376 } } ], "vout": [ { "amount": 461486124854, "target": { "key": "d06884cc67cd2ba3e61b015cd8389221d5ff7511beffef32ff5d7179c313d3a9" } } ], "extra": [ 1, 141, 211, 125, 143, 207, 6, 187, 18, 185, 237, 119, 143, 204, 166, 58, 185, 54, 122, 222, 65, 10, 112, 219, 90, 68, 220, 223, 201, 175, 77, 184, 227, 2, 17, 0, 0, 0, 12, 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