Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7f01f5cdca4fe66d4c7531c33928cad7f2922f4175ee7e33324d3e64b7a417

Tx prefix hash: b4a89a7953bcd941304b327781ead236f27202f7d91c929befa39617ce943cfb
Tx public key: bcb6b2455e443e31d320b70190a57e49d6645c86548c64e90a6b3b889971a1e0
Timestamp: 1740177569 Timestamp [UCT]: 2025-02-21 22:39:29 Age [y:d:h:m:s]: 00:318:00:03:51
Block: 1224365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225140 RingCT/type: yes/0
Extra: 01bcb6b2455e443e31d320b70190a57e49d6645c86548c64e90a6b3b889971a1e00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a228b580fd4d052960945802cfe26129609bf25fbb0c9f95029878f5e2b99d 0.600000000000 1711224 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": 1224375, "vin": [ { "gen": { "height": 1224365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a228b580fd4d052960945802cfe26129609bf25fbb0c9f95029878f5e2b99d" } } ], "extra": [ 1, 188, 182, 178, 69, 94, 68, 62, 49, 211, 32, 183, 1, 144, 165, 126, 73, 214, 100, 92, 134, 84, 140, 100, 233, 10, 107, 59, 136, 153, 113, 161, 224, 2, 17, 0, 0, 0, 2, 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