Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8844b33f4bcfc24175b9ce4ee124b0e57474df7f3cb87cc947ce28abb8c1051d

Tx prefix hash: f25e95705024e9c4a8f65ecf8b315d3781112a376c31e45bf32cfa1611ffe2a5
Tx public key: 2307104be64d5ac2bd3f224ca4b12708c01b1a41af35fe1f12eb0fef24dc53be
Timestamp: 1674304449 Timestamp [UCT]: 2023-01-21 12:34:09 Age [y:d:h:m:s]: 01:304:03:58:22
Block: 679579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478365 RingCT/type: yes/0
Extra: 012307104be64d5ac2bd3f224ca4b12708c01b1a41af35fe1f12eb0fef24dc53be021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.437736692000 dcy

stealth address amount amount idx
00: fa153078fd549a13ebf1484e0753b2ad0a5217f8ee10dd9e27153891340fdb3f 3.437736692000 1121582 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": 679589, "vin": [ { "gen": { "height": 679579 } } ], "vout": [ { "amount": 3437736692, "target": { "key": "fa153078fd549a13ebf1484e0753b2ad0a5217f8ee10dd9e27153891340fdb3f" } } ], "extra": [ 1, 35, 7, 16, 75, 230, 77, 90, 194, 189, 63, 34, 76, 164, 177, 39, 8, 192, 27, 26, 65, 175, 53, 254, 31, 18, 235, 15, 239, 36, 220, 83, 190, 2, 17, 0, 0, 0, 2, 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