Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9a549b245aee2ef589f4b2040c54945801d97d652dfcab074836b88e9d8fa6

Tx prefix hash: 479660bdd9d061e50affda6b298a9f916e76c06533dbe200204c3dfc95a4ca36
Tx public key: 4c44d19f2bdc196c75522a05119b8a1f775bda9291abd18f130c45e8d59dfbc8
Timestamp: 1702526370 Timestamp [UCT]: 2023-12-14 03:59:30 Age [y:d:h:m:s]: 01:184:22:54:01
Block: 912690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393279 RingCT/type: yes/0
Extra: 014c44d19f2bdc196c75522a05119b8a1f775bda9291abd18f130c45e8d59dfbc8021100000010faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61048a56418def912da1e4bc6f977f74760c6e121abb0b6109dca09d478d4322 0.600000000000 1369924 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": 912700, "vin": [ { "gen": { "height": 912690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61048a56418def912da1e4bc6f977f74760c6e121abb0b6109dca09d478d4322" } } ], "extra": [ 1, 76, 68, 209, 159, 43, 220, 25, 108, 117, 82, 42, 5, 17, 155, 138, 31, 119, 91, 218, 146, 145, 171, 209, 143, 19, 12, 69, 232, 213, 157, 251, 200, 2, 17, 0, 0, 0, 16, 250, 243, 92, 156, 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