Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76839a5182ba1d08a2366e8ddb8eb47bdf64ab13cf06f26a0b50a497202b8e12

Tx prefix hash: 5cf069680f4ae1d6122b12d3f7f1a575a5bb0bcb848d06fff6de503dce91cc0b
Tx public key: aa7621dd2e1f7b7d3f1e15877d2036e1346cae77057183f2e3ce86bf37f398f3
Timestamp: 1760873186 Timestamp [UCT]: 2025-10-19 11:26:26 Age [y:d:h:m:s]: 00:105:00:46:58
Block: 1393313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75000 RingCT/type: yes/0
Extra: 01aa7621dd2e1f7b7d3f1e15877d2036e1346cae77057183f2e3ce86bf37f398f302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a8ab7f651a60c584ae60bd762b81ea84625f24cdb2101cdd8eb538a2bf8e8d9 0.600000000000 1881576 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": 1393323, "vin": [ { "gen": { "height": 1393313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a8ab7f651a60c584ae60bd762b81ea84625f24cdb2101cdd8eb538a2bf8e8d9" } } ], "extra": [ 1, 170, 118, 33, 221, 46, 31, 123, 125, 63, 30, 21, 135, 125, 32, 54, 225, 52, 108, 174, 119, 5, 113, 131, 242, 227, 206, 134, 191, 55, 243, 152, 243, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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