Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b177c025bead80ae907a072001ca4cc1f941e4e2316c0b5e958fc41e1415c405

Tx prefix hash: 30a3b24d81710d4e94eed24be425e30d74a936bfec40dfe3d2654184f84e015b
Tx public key: 6c15e74a8a16ee3b4bc376e47806727273f2bf6043383ecc6d8669578fc93d94
Timestamp: 1707214980 Timestamp [UCT]: 2024-02-06 10:23:00 Age [y:d:h:m:s]: 01:091:15:40:16
Block: 951555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326580 RingCT/type: yes/0
Extra: 016c15e74a8a16ee3b4bc376e47806727273f2bf6043383ecc6d8669578fc93d9402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb412493b5e20e0d7d5ca12b863a582fdeabaf437416d093a900903ebaf4009 0.600000000000 1410335 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": 951565, "vin": [ { "gen": { "height": 951555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb412493b5e20e0d7d5ca12b863a582fdeabaf437416d093a900903ebaf4009" } } ], "extra": [ 1, 108, 21, 231, 74, 138, 22, 238, 59, 75, 195, 118, 228, 120, 6, 114, 114, 115, 242, 191, 96, 67, 56, 62, 204, 109, 134, 105, 87, 143, 201, 61, 148, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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