Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 220baf04acbd0ff5080879ff58347056065b818f6f28413d69957f3d1ca84861

Tx prefix hash: 50ffc71a4d3d3fb396ac4e091eb3ae176435ea4e68da4d7a0d5eda59f4758797
Tx public key: 3691283a3a00296e59cb5b955e64565544c237c914fe05165712a62d0d59aed8
Timestamp: 1681745884 Timestamp [UCT]: 2023-04-17 15:38:04 Age [y:d:h:m:s]: 01:356:23:46:00
Block: 740652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516422 RingCT/type: yes/0
Extra: 013691283a3a00296e59cb5b955e64565544c237c914fe05165712a62d0d59aed8021100000002b3164c24000000000000000000

1 output(s) for total of 2.157310621000 dcy

stealth address amount amount idx
00: ca8d9b7b989d136b2377e88e7edf8445b48bad6a40e14d900f0c4c9eb7b65dd4 2.157310621000 1187551 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": 740662, "vin": [ { "gen": { "height": 740652 } } ], "vout": [ { "amount": 2157310621, "target": { "key": "ca8d9b7b989d136b2377e88e7edf8445b48bad6a40e14d900f0c4c9eb7b65dd4" } } ], "extra": [ 1, 54, 145, 40, 58, 58, 0, 41, 110, 89, 203, 91, 149, 94, 100, 86, 85, 68, 194, 55, 201, 20, 254, 5, 22, 87, 18, 166, 45, 13, 89, 174, 216, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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