Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b71fd040deaac601d6639e2d2025ef0daae23c10a7a7f4e99468625ca0813a98

Tx prefix hash: 2c6e4dabe0157adcbe7b1e53cc8ee0a48fd1b699e720196d7e811b0359a6e4ac
Tx public key: 4203fb6511cf36f558314e7f05e7d620ad85cde1703337cd3a93364f63918127
Timestamp: 1722366089 Timestamp [UCT]: 2024-07-30 19:01:29 Age [y:d:h:m:s]: 00:250:11:56:35
Block: 1077168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178933 RingCT/type: yes/0
Extra: 014203fb6511cf36f558314e7f05e7d620ad85cde1703337cd3a93364f6391812702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 309f197e9860b6653c53b0fe29609c32f1c1e4f9a0a40534cd9189300efe119f 0.600000000000 1549715 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": 1077178, "vin": [ { "gen": { "height": 1077168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "309f197e9860b6653c53b0fe29609c32f1c1e4f9a0a40534cd9189300efe119f" } } ], "extra": [ 1, 66, 3, 251, 101, 17, 207, 54, 245, 88, 49, 78, 127, 5, 231, 214, 32, 173, 133, 205, 225, 112, 51, 55, 205, 58, 147, 54, 79, 99, 145, 129, 39, 2, 17, 0, 0, 0, 10, 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