Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ae54c00f6e5daad5248bddbb12de3fca36759eee88e055316ebdf6a05f242ba

Tx prefix hash: e8e516906f19f9afa57cef9cb21759dbef1fbdf6098d83d0337b134eae6a8ff3
Tx public key: cf483802f4f31ed2a01bbc5598a6770aa3dd19ec183d6c5e49744d3c5d76e8b7
Timestamp: 1580600475 Timestamp [UCT]: 2020-02-01 23:41:15 Age [y:d:h:m:s]: 04:300:07:09:31
Block: 56784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105878 RingCT/type: yes/0
Extra: 01cf483802f4f31ed2a01bbc5598a6770aa3dd19ec183d6c5e49744d3c5d76e8b7021100000003d81c26c0000000000000000000

1 output(s) for total of 397.971396359000 dcy

stealth address amount amount idx
00: 76af5b8fb850c8d533709eb47b3ced7126cbaba77acff026ad02b897f366af3d 397.971396359000 104707 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": 56794, "vin": [ { "gen": { "height": 56784 } } ], "vout": [ { "amount": 397971396359, "target": { "key": "76af5b8fb850c8d533709eb47b3ced7126cbaba77acff026ad02b897f366af3d" } } ], "extra": [ 1, 207, 72, 56, 2, 244, 243, 30, 210, 160, 27, 188, 85, 152, 166, 119, 10, 163, 221, 25, 236, 24, 61, 108, 94, 73, 116, 77, 60, 93, 118, 232, 183, 2, 17, 0, 0, 0, 3, 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