Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33cd1f1db9501207e0f5872ca4f468deb5b5cb80df4af57f644990e9928f9261

Tx prefix hash: 0d3adb53a45dcce98d6afaa65c59a8ed83735b30f72118a572e50bb0d8a5df34
Tx public key: 5d3d6b9efb7e8433bf759b8740c496245fa40afb80adba91d3fe99437cc4d72a
Timestamp: 1723444901 Timestamp [UCT]: 2024-08-12 06:41:41 Age [y:d:h:m:s]: 00:249:02:28:09
Block: 1086108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177931 RingCT/type: yes/0
Extra: 015d3d6b9efb7e8433bf759b8740c496245fa40afb80adba91d3fe99437cc4d72a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae9daad5daee423e3520e152c938d45402dfb9665d4a5682dda031ab236df22 0.600000000000 1560701 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": 1086118, "vin": [ { "gen": { "height": 1086108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae9daad5daee423e3520e152c938d45402dfb9665d4a5682dda031ab236df22" } } ], "extra": [ 1, 93, 61, 107, 158, 251, 126, 132, 51, 191, 117, 155, 135, 64, 196, 150, 36, 95, 164, 10, 251, 128, 173, 186, 145, 211, 254, 153, 67, 124, 196, 215, 42, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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