Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d5e88d8381660f1b4e456e200f80118127db1276b8726224e2b8b71ca390f1

Tx prefix hash: b67aed67ffb0a05be184c3a99dd1bf58a951b9db39a5ac17c98ea58289e005c2
Tx public key: 16f0e5b237caeae7b1611d36ee72feeaf8437a3f3324fef006f353ed7b9b1c1c
Timestamp: 1762059914 Timestamp [UCT]: 2025-11-02 05:05:14 Age [y:d:h:m:s]: 00:004:17:10:20
Block: 1403138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3367 RingCT/type: yes/0
Extra: 0116f0e5b237caeae7b1611d36ee72feeaf8437a3f3324fef006f353ed7b9b1c1c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 013860a24759e252a529a3b4cbb6d5f44f0b43bed3dbca405cbb218b22026c7a 0.600000000000 1891465 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": 1403148, "vin": [ { "gen": { "height": 1403138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "013860a24759e252a529a3b4cbb6d5f44f0b43bed3dbca405cbb218b22026c7a" } } ], "extra": [ 1, 22, 240, 229, 178, 55, 202, 234, 231, 177, 97, 29, 54, 238, 114, 254, 234, 248, 67, 122, 63, 51, 36, 254, 240, 6, 243, 83, 237, 123, 155, 28, 28, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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