Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4fdfa78ab831913a2e957b6367f083d0eaa1b14b6c407bebd71ae9a8f71744a

Tx prefix hash: bd0085593f9d147c90a74c41f35d88ea4482766ad8e0e0f532cfc9ec26a32f0c
Tx public key: c09e5d0eff8127a79c53cf0246d3c41891863255a0bf205dbe71ee372258741e
Timestamp: 1648522823 Timestamp [UCT]: 2022-03-29 03:00:23 Age [y:d:h:m:s]: 02:237:11:24:57
Block: 468635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689244 RingCT/type: yes/0
Extra: 01c09e5d0eff8127a79c53cf0246d3c41891863255a0bf205dbe71ee372258741e02110000000a4a0f5013000000000000000000

1 output(s) for total of 17.187707601000 dcy

stealth address amount amount idx
00: a70fc8955e37d4243b018dbabd6b055ef70052541a39239066df94c5f16c09a9 17.187707601000 887391 of 0

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": 468645, "vin": [ { "gen": { "height": 468635 } } ], "vout": [ { "amount": 17187707601, "target": { "key": "a70fc8955e37d4243b018dbabd6b055ef70052541a39239066df94c5f16c09a9" } } ], "extra": [ 1, 192, 158, 93, 14, 255, 129, 39, 167, 156, 83, 207, 2, 70, 211, 196, 24, 145, 134, 50, 85, 160, 191, 32, 93, 190, 113, 238, 55, 34, 88, 116, 30, 2, 17, 0, 0, 0, 10, 74, 15, 80, 19, 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