Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa7b3ee160dc15a91824ce4ba453d765722918ca16bef31de9c97b3fb89d5220

Tx prefix hash: 681b6835a118f35231a01d5d8a5540b48a539e7682f320a091bfa8c4da18552e
Tx public key: 983d818d3749d90b6e9c8156230b51e9239b081c905ab590e416d5d2a27d49e2
Timestamp: 1745141443 Timestamp [UCT]: 2025-04-20 09:30:43 Age [y:d:h:m:s]: 00:202:10:19:49
Block: 1265479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142385 RingCT/type: yes/0
Extra: 01983d818d3749d90b6e9c8156230b51e9239b081c905ab590e416d5d2a27d49e20211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7dcf58fcbf59e06da2ff982437f8bb10e7ea0ec1068b90e3f86a377be29ecf2 0.600000000000 1752688 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": 1265489, "vin": [ { "gen": { "height": 1265479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7dcf58fcbf59e06da2ff982437f8bb10e7ea0ec1068b90e3f86a377be29ecf2" } } ], "extra": [ 1, 152, 61, 129, 141, 55, 73, 217, 11, 110, 156, 129, 86, 35, 11, 81, 233, 35, 155, 8, 28, 144, 90, 181, 144, 228, 22, 213, 210, 162, 125, 73, 226, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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