Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb69d18d3cbadd542982e6f203c5a294d88a20fe7de24aa0bd66d14af80bae71

Tx prefix hash: 289eb46003ab85bd972415aed8fe610d9ab7196a8b22d48381a385f404ee6e21
Tx public key: 7342a685b30c949e0bca28a2bf7d422f1678e4ea0a60b9b967523ff018b16276
Timestamp: 1737435732 Timestamp [UCT]: 2025-01-21 05:02:12 Age [y:d:h:m:s]: 00:148:18:49:01
Block: 1201907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106069 RingCT/type: yes/0
Extra: 017342a685b30c949e0bca28a2bf7d422f1678e4ea0a60b9b967523ff018b162760211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863468e763cef5c46118f56aacd284fcb70635fd54d3731dcee214c314edfcd8 0.600000000000 1688566 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": 1201917, "vin": [ { "gen": { "height": 1201907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863468e763cef5c46118f56aacd284fcb70635fd54d3731dcee214c314edfcd8" } } ], "extra": [ 1, 115, 66, 166, 133, 179, 12, 148, 158, 11, 202, 40, 162, 191, 125, 66, 47, 22, 120, 228, 234, 10, 96, 185, 185, 103, 82, 63, 240, 24, 177, 98, 118, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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