Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7624191886010e5ec6d43673511c06874d8c0b02939fb0874dde3f74c46764bd

Tx prefix hash: 8e3c0fcbc88787656a653da32897d02560a55c31af4e8fd89d6e565e3885a44a
Tx public key: 31a8d7fb8ada01ac9bd880102c1b19e378895ecb2de1d5cd1521e1e45e84d14d
Timestamp: 1705309930 Timestamp [UCT]: 2024-01-15 09:12:10 Age [y:d:h:m:s]: 01:155:15:29:35
Block: 935753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372255 RingCT/type: yes/0
Extra: 0131a8d7fb8ada01ac9bd880102c1b19e378895ecb2de1d5cd1521e1e45e84d14d0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0a9f3cfc8edfd1f9ebde148251f0d507c0bdfe9d6fb95df01280f4ea31089fe 0.600000000000 1393769 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": 935763, "vin": [ { "gen": { "height": 935753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0a9f3cfc8edfd1f9ebde148251f0d507c0bdfe9d6fb95df01280f4ea31089fe" } } ], "extra": [ 1, 49, 168, 215, 251, 138, 218, 1, 172, 155, 216, 128, 16, 44, 27, 25, 227, 120, 137, 94, 203, 45, 225, 213, 205, 21, 33, 225, 228, 94, 132, 209, 77, 2, 17, 0, 0, 0, 8, 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