Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b79b1515e2fff2ce4a2fe06d1786068770a6f37fcc6382ba58078675713ea9be

Tx prefix hash: 6c39d325e45cf2cda74337bd615ee661898344588bd38b39a3cedbe98b4fcf09
Tx public key: d07c3a3c0d9c37725d3f6cc913f663b4f80dbbe447f588610a110161495cc965
Timestamp: 1743473670 Timestamp [UCT]: 2025-04-01 02:14:30 Age [y:d:h:m:s]: 00:221:09:07:54
Block: 1251666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155942 RingCT/type: yes/0
Extra: 01d07c3a3c0d9c37725d3f6cc913f663b4f80dbbe447f588610a110161495cc96502110000000aa2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c72dc53e14e73f9fd22a9964f9e39730ea09db0b907cb6fbf093c24a5a65e6 0.600000000000 1738735 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": 1251676, "vin": [ { "gen": { "height": 1251666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c72dc53e14e73f9fd22a9964f9e39730ea09db0b907cb6fbf093c24a5a65e6" } } ], "extra": [ 1, 208, 124, 58, 60, 13, 156, 55, 114, 93, 63, 108, 201, 19, 246, 99, 180, 248, 13, 187, 228, 71, 245, 136, 97, 10, 17, 1, 97, 73, 92, 201, 101, 2, 17, 0, 0, 0, 10, 162, 237, 1, 107, 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