Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866642e469b78f111fa3487937000740bbea9eb72fc61e623669e47327ba055f

Tx prefix hash: 97a1ce64cfe70bec78f0695e748b8fee6fd9de7b01cbe3287743efdb9d8fc053
Tx public key: 0eb334ab095f6a9d6d73c3ec5f65767bb2c5638e78de7cac1d81e4461cd4f8f3
Timestamp: 1722523531 Timestamp [UCT]: 2024-08-01 14:45:31 Age [y:d:h:m:s]: 00:205:22:58:56
Block: 1078477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147054 RingCT/type: yes/0
Extra: 010eb334ab095f6a9d6d73c3ec5f65767bb2c5638e78de7cac1d81e4461cd4f8f3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b611be8111a8f68e288b46d15ed81b8dd065ab656e22dcb81e01e1d8959f3a 0.600000000000 1551056 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": 1078487, "vin": [ { "gen": { "height": 1078477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b611be8111a8f68e288b46d15ed81b8dd065ab656e22dcb81e01e1d8959f3a" } } ], "extra": [ 1, 14, 179, 52, 171, 9, 95, 106, 157, 109, 115, 195, 236, 95, 101, 118, 123, 178, 197, 99, 142, 120, 222, 124, 172, 29, 129, 228, 70, 28, 212, 248, 243, 2, 17, 0, 0, 0, 5, 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