Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9880ca6604c3916dcc59e3dc025141f900cc3eb93f1a850e5f414e4e9333378e

Tx prefix hash: b894461b198f1b72f1eb865cd1581e425986c1715a78c626e7f94a9b8e7b4497
Tx public key: 9701b6ff34bd2cda92207bf206d4a067c0f456a64b5b4090ea1a4a7bef923c74
Timestamp: 1704090849 Timestamp [UCT]: 2024-01-01 06:34:09 Age [y:d:h:m:s]: 01:004:21:31:33
Block: 925653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264835 RingCT/type: yes/0
Extra: 019701b6ff34bd2cda92207bf206d4a067c0f456a64b5b4090ea1a4a7bef923c74021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e604ad6a0de5f9d27b07acbc69d61a51a398e2a6ee8d72d3e8d197e1f7ec59b 0.600000000000 1383417 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": 925663, "vin": [ { "gen": { "height": 925653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e604ad6a0de5f9d27b07acbc69d61a51a398e2a6ee8d72d3e8d197e1f7ec59b" } } ], "extra": [ 1, 151, 1, 182, 255, 52, 189, 44, 218, 146, 32, 123, 242, 6, 212, 160, 103, 192, 244, 86, 166, 75, 91, 64, 144, 234, 26, 74, 123, 239, 146, 60, 116, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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