Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e19fa768c8219c778b5dbc3645e5940a047f34245cd8f26e43cc1f0aef801dc

Tx prefix hash: beba9e044e5ab6229026da2b66d777d99c0cb7ccdfcfb03f3e01c6a66243fc22
Tx public key: a0fd829359865745a1200676dacfabd0aec2f1166c3b416b513c67bd4175541f
Timestamp: 1578242939 Timestamp [UCT]: 2020-01-05 16:48:59 Age [y:d:h:m:s]: 05:029:11:09:57
Block: 39327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170914 RingCT/type: yes/0
Extra: 01a0fd829359865745a1200676dacfabd0aec2f1166c3b416b513c67bd4175541f02110000000a4ac5aa02000000000000000000

1 output(s) for total of 454.667772836000 dcy

stealth address amount amount idx
00: 24208a92d74e2e5abf399f7629afbaa32c599b6b97414a6761facc6988316a35 454.667772836000 67739 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": 39337, "vin": [ { "gen": { "height": 39327 } } ], "vout": [ { "amount": 454667772836, "target": { "key": "24208a92d74e2e5abf399f7629afbaa32c599b6b97414a6761facc6988316a35" } } ], "extra": [ 1, 160, 253, 130, 147, 89, 134, 87, 69, 161, 32, 6, 118, 218, 207, 171, 208, 174, 194, 241, 22, 108, 59, 65, 107, 81, 60, 103, 189, 65, 117, 84, 31, 2, 17, 0, 0, 0, 10, 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