Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60ba08a00a0e42e5f3ab022a59a92ffbd009839f20f2d7c9d260c0db53f39c4f

Tx prefix hash: f5ffd01a7019ac54d6b8a60e31c08b52fb09a63df88fa90151366d7e1a0995a4
Tx public key: 55e6e9b243b9c4e76e4b4fd11f1c984c39a40fa9cdf75e8c22f86d83d5903b95
Timestamp: 1717844685 Timestamp [UCT]: 2024-06-08 11:04:45 Age [y:d:h:m:s]: 00:297:14:10:09
Block: 1039689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212661 RingCT/type: yes/0
Extra: 0155e6e9b243b9c4e76e4b4fd11f1c984c39a40fa9cdf75e8c22f86d83d5903b950211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7702d9272440124a04938b7fc5e83eb97359dd514ae80aab4a51c426553dffe 0.600000000000 1508340 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": 1039699, "vin": [ { "gen": { "height": 1039689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7702d9272440124a04938b7fc5e83eb97359dd514ae80aab4a51c426553dffe" } } ], "extra": [ 1, 85, 230, 233, 178, 67, 185, 196, 231, 110, 75, 79, 209, 31, 28, 152, 76, 57, 164, 15, 169, 205, 247, 94, 140, 34, 248, 109, 131, 213, 144, 59, 149, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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