Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52abdcc717639bc6b4f40d1f951f0be204bb49a1b0b413984352317350d1819

Tx prefix hash: 3591fded175d5ddd7c2f259d69d9c82961afe67ee20124cddbd208668dbae6a6
Tx public key: 2bca931aa1ea2f0200b9225311f2691287e4bc0a1c53debe4694b5e54a732e93
Timestamp: 1763459579 Timestamp [UCT]: 2025-11-18 09:52:59 Age [y:d:h:m:s]: 00:003:07:03:16
Block: 1414728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2351 RingCT/type: yes/0
Extra: 012bca931aa1ea2f0200b9225311f2691287e4bc0a1c53debe4694b5e54a732e93021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f0bbd8236caafc4647dd0f5331c4cc34f78a22f78cebca57ca904fa4397d021 0.600000000000 1903219 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": 1414738, "vin": [ { "gen": { "height": 1414728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0bbd8236caafc4647dd0f5331c4cc34f78a22f78cebca57ca904fa4397d021" } } ], "extra": [ 1, 43, 202, 147, 26, 161, 234, 47, 2, 0, 185, 34, 83, 17, 242, 105, 18, 135, 228, 188, 10, 28, 83, 222, 190, 70, 148, 181, 229, 74, 115, 46, 147, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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