Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c2196bbd626e3206bfee92a3ec83049f8a2adf7cbf54673bb1fc440699e8a9f

Tx prefix hash: 74a25fde1a67a1747e8054f1a941866cb464c07c0ca0fe167dd93a2076b397ef
Tx public key: bca34ebea1499e7d0d553f4d98f275b602b5ad0fffb27313fb16372fc56ed268
Timestamp: 1736801138 Timestamp [UCT]: 2025-01-13 20:45:38 Age [y:d:h:m:s]: 00:309:03:08:05
Block: 1196707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218444 RingCT/type: yes/0
Extra: 01bca34ebea1499e7d0d553f4d98f275b602b5ad0fffb27313fb16372fc56ed2680211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf34e9549459346ac09c55d3dfef786cd573f43adc09699ed2d42fe855ca323e 0.600000000000 1683308 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": 1196717, "vin": [ { "gen": { "height": 1196707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf34e9549459346ac09c55d3dfef786cd573f43adc09699ed2d42fe855ca323e" } } ], "extra": [ 1, 188, 163, 78, 190, 161, 73, 158, 125, 13, 85, 63, 77, 152, 242, 117, 182, 2, 181, 173, 15, 255, 178, 115, 19, 251, 22, 55, 47, 197, 110, 210, 104, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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