Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4ab475ce3a1be4b21cadcbf30f01b9757fad053e356868f0d78e79b838e0d4d

Tx prefix hash: 06b5bfac7ef6a473249e9931e13e06dd1cdf64f97301dc15c38f311eb6e3601c
Tx public key: 99bc3103b2a7b6ef346198e86cf6c4c1f788639b0f7d90fa01d8043154bcef3a
Timestamp: 1721807161 Timestamp [UCT]: 2024-07-24 07:46:01 Age [y:d:h:m:s]: 00:275:20:43:51
Block: 1072529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197088 RingCT/type: yes/0
Extra: 0199bc3103b2a7b6ef346198e86cf6c4c1f788639b0f7d90fa01d8043154bcef3a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3950a3c8ee486f74b8ab5f7216cc751592ca07736d5aee864c6a8e13052608a 0.600000000000 1545002 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": 1072539, "vin": [ { "gen": { "height": 1072529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3950a3c8ee486f74b8ab5f7216cc751592ca07736d5aee864c6a8e13052608a" } } ], "extra": [ 1, 153, 188, 49, 3, 178, 167, 182, 239, 52, 97, 152, 232, 108, 246, 196, 193, 247, 136, 99, 155, 15, 125, 144, 250, 1, 216, 4, 49, 84, 188, 239, 58, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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