Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c712c36576207b57fe2182c5c53fb67d3a87470b7647637bddf0220db4cf1b24

Tx prefix hash: 5303accdc2b2f3840719505067eb9cf0682ea8058bdf2debfdd9150a65428b44
Tx public key: 3c54d82d5e7af429d8dfd874644bee86d7105115e6b45dd79e1e74b2f73fdfce
Timestamp: 1722104423 Timestamp [UCT]: 2024-07-27 18:20:23 Age [y:d:h:m:s]: 01:109:14:32:03
Block: 1075003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336837 RingCT/type: yes/0
Extra: 013c54d82d5e7af429d8dfd874644bee86d7105115e6b45dd79e1e74b2f73fdfce021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f89c8d775bae5b381426748b49d4081aad74e6a02632cdcf044bbb33402edea5 0.600000000000 1547522 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": 1075013, "vin": [ { "gen": { "height": 1075003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f89c8d775bae5b381426748b49d4081aad74e6a02632cdcf044bbb33402edea5" } } ], "extra": [ 1, 60, 84, 216, 45, 94, 122, 244, 41, 216, 223, 216, 116, 100, 75, 238, 134, 215, 16, 81, 21, 230, 180, 93, 215, 158, 30, 116, 178, 247, 63, 223, 206, 2, 17, 0, 0, 0, 7, 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