Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8138177c2dd8ecfe24a897d10248e24953896d2ac8f09061963503311a5a8ac7

Tx prefix hash: 59dfcd3a41cd68984210a26670787d2b8f07bb796bf4f4d3549490975426eca5
Tx public key: a286ea0d8d3b6a09668f17b81959d90b3f975edb3d59b204c47ef0b42fb42d2f
Timestamp: 1722742668 Timestamp [UCT]: 2024-08-04 03:37:48 Age [y:d:h:m:s]: 00:243:13:51:35
Block: 1080297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173971 RingCT/type: yes/0
Extra: 01a286ea0d8d3b6a09668f17b81959d90b3f975edb3d59b204c47ef0b42fb42d2f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abbf3f20377adc892a17e5226ad609eaa93a4d050d3880151323af9718a94734 0.600000000000 1553594 of 15

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": 1080307, "vin": [ { "gen": { "height": 1080297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abbf3f20377adc892a17e5226ad609eaa93a4d050d3880151323af9718a94734" } } ], "extra": [ 1, 162, 134, 234, 13, 141, 59, 106, 9, 102, 143, 23, 184, 25, 89, 217, 11, 63, 151, 94, 219, 61, 89, 178, 4, 196, 126, 240, 180, 47, 180, 45, 47, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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