Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8f5aa42e4b4e5dafe132cbd2006bd15d7fc53d002a555e6bb24d7f8644d2ca

Tx prefix hash: 8901d68e09944ee16dba05f98094039099b141fac33dc1a5ae105f4066fb4022
Tx public key: 77fe1e079b627859f8905eeb33dc7581ce37294353ab089fa9f90826a0afad3c
Timestamp: 1701253945 Timestamp [UCT]: 2023-11-29 10:32:25 Age [y:d:h:m:s]: 01:128:23:12:19
Block: 902134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353340 RingCT/type: yes/0
Extra: 0177fe1e079b627859f8905eeb33dc7581ce37294353ab089fa9f90826a0afad3c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.629296831000 dcy

stealth address amount amount idx
00: 39fd79b02d791d196f86908904510b0f7faafe9f90cc0f522b79b29544b207a4 0.629296831000 1358749 of 0

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": 902144, "vin": [ { "gen": { "height": 902134 } } ], "vout": [ { "amount": 629296831, "target": { "key": "39fd79b02d791d196f86908904510b0f7faafe9f90cc0f522b79b29544b207a4" } } ], "extra": [ 1, 119, 254, 30, 7, 155, 98, 120, 89, 248, 144, 94, 235, 51, 220, 117, 129, 206, 55, 41, 67, 83, 171, 8, 159, 169, 249, 8, 38, 160, 175, 173, 60, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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