Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32344d3b520f72b3f02d1677070abe533fd93dd48c85a33b2e9d87ddcfc4c93f

Tx prefix hash: 1c0fd261dbd10f885d355cbb8a2e7d82b9e5d3f48fb74585e8efd07973de3491
Tx public key: f4f552a6cb9b3ccf969575349424e7456000b8f8561a6dd587d170470fa035f3
Timestamp: 1698535547 Timestamp [UCT]: 2023-10-28 23:25:47 Age [y:d:h:m:s]: 01:234:00:25:26
Block: 879820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428156 RingCT/type: yes/0
Extra: 01f4f552a6cb9b3ccf969575349424e7456000b8f8561a6dd587d170470fa035f3021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.746089834000 dcy

stealth address amount amount idx
00: f2694632f7d89b62fa6968775f80a62fa435804acce6eba734c55eca4cb150d3 0.746089834000 1335360 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": 879830, "vin": [ { "gen": { "height": 879820 } } ], "vout": [ { "amount": 746089834, "target": { "key": "f2694632f7d89b62fa6968775f80a62fa435804acce6eba734c55eca4cb150d3" } } ], "extra": [ 1, 244, 245, 82, 166, 203, 155, 60, 207, 150, 149, 117, 52, 148, 36, 231, 69, 96, 0, 184, 248, 86, 26, 109, 213, 135, 209, 112, 71, 15, 160, 53, 243, 2, 17, 0, 0, 0, 4, 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