Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32d0e0777f1a5e359be3c9b77b5dffd31d47493257c8af6a7e98a18642ee035b

Tx prefix hash: 4e66390274a9670135577b875d3e4d30056b1527ce1d9b476235c86fde7be634
Tx public key: dcfd5f224d86beefa1f1cf4861c76ff7a4ae1887f1d0b6300e31dc91af8b0edc
Timestamp: 1709410762 Timestamp [UCT]: 2024-03-02 20:19:22 Age [y:d:h:m:s]: 01:107:10:49:02
Block: 969773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337722 RingCT/type: yes/0
Extra: 01dcfd5f224d86beefa1f1cf4861c76ff7a4ae1887f1d0b6300e31dc91af8b0edc02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 341a0f9161ad5d82a15ce7d1cdadcd8a1ef456b662b9f5424af3d1d113486874 0.600000000000 1429616 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": 969783, "vin": [ { "gen": { "height": 969773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "341a0f9161ad5d82a15ce7d1cdadcd8a1ef456b662b9f5424af3d1d113486874" } } ], "extra": [ 1, 220, 253, 95, 34, 77, 134, 190, 239, 161, 241, 207, 72, 97, 199, 111, 247, 164, 174, 24, 135, 241, 208, 182, 48, 14, 49, 220, 145, 175, 139, 14, 220, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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