Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebc52755fb417b6e53d9e2270d1a125c4c420dddc775626edab9e77b4d0b2827

Tx prefix hash: a904dc9ae4f138c36b426b358c49b5b9fe3c1416f61eb1c79be63cdbafc10f4f
Tx public key: b3d3e2075e229d362aeb5f9e349153dc435448a3dd06f9486e1e3bc442a94255
Timestamp: 1697368126 Timestamp [UCT]: 2023-10-15 11:08:46 Age [y:d:h:m:s]: 01:164:22:06:16
Block: 870130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378890 RingCT/type: yes/0
Extra: 01b3d3e2075e229d362aeb5f9e349153dc435448a3dd06f9486e1e3bc442a94255021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.803337664000 dcy

stealth address amount amount idx
00: a0b0db62d7e6957c2ee0bfe1d50d59f4922b51b0e8a6ed9c53675dbb6fc47146 0.803337664000 1325003 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": 870140, "vin": [ { "gen": { "height": 870130 } } ], "vout": [ { "amount": 803337664, "target": { "key": "a0b0db62d7e6957c2ee0bfe1d50d59f4922b51b0e8a6ed9c53675dbb6fc47146" } } ], "extra": [ 1, 179, 211, 226, 7, 94, 34, 157, 54, 42, 235, 95, 158, 52, 145, 83, 220, 67, 84, 72, 163, 221, 6, 249, 72, 110, 30, 59, 196, 66, 169, 66, 85, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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