Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987cd40b3ff31ed4c5f5ab74ed693c8dee817726b65de27a45d3303e1634f72c

Tx prefix hash: ffa1541476f3b46700815eddad6232fc61136536eee6fe9c73a1ad13661d8dfe
Tx public key: cc9c11fe66eb1c9d8bd7060f4c03db2db95a87c706f4981ef82b7eecd03ae733
Timestamp: 1708937450 Timestamp [UCT]: 2024-02-26 08:50:50 Age [y:d:h:m:s]: 00:364:08:42:52
Block: 965846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260520 RingCT/type: yes/0
Extra: 01cc9c11fe66eb1c9d8bd7060f4c03db2db95a87c706f4981ef82b7eecd03ae73302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc2b7ee570d6c996c48d8f0b41e97c47a4ebe4183a64a5072549529beaa4aebc 0.600000000000 1425601 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": 965856, "vin": [ { "gen": { "height": 965846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc2b7ee570d6c996c48d8f0b41e97c47a4ebe4183a64a5072549529beaa4aebc" } } ], "extra": [ 1, 204, 156, 17, 254, 102, 235, 28, 157, 139, 215, 6, 15, 76, 3, 219, 45, 185, 90, 135, 199, 6, 244, 152, 30, 248, 43, 126, 236, 208, 58, 231, 51, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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