Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc9a50e997f71e9008ae1bd6f7da78b1c2ac7a99e08c6153c083afc9e62e69ce

Tx prefix hash: 48517556c290a347226e4776461e43e778512d8b48492d692fc552bd43177704
Tx public key: 89f41945746d91ad2f5cbb92b4f9136deb2a78ae62a148a94cb6787ccdf60bda
Timestamp: 1733005705 Timestamp [UCT]: 2024-11-30 22:28:25 Age [y:d:h:m:s]: 00:028:19:58:25
Block: 1165278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20618 RingCT/type: yes/0
Extra: 0189f41945746d91ad2f5cbb92b4f9136deb2a78ae62a148a94cb6787ccdf60bda0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09be531f4307ea0b5aa6174c842d1cc2c79aada6ddecc0c1d902a411f23c41ea 0.600000000000 1650953 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": 1165288, "vin": [ { "gen": { "height": 1165278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09be531f4307ea0b5aa6174c842d1cc2c79aada6ddecc0c1d902a411f23c41ea" } } ], "extra": [ 1, 137, 244, 25, 69, 116, 109, 145, 173, 47, 92, 187, 146, 180, 249, 19, 109, 235, 42, 120, 174, 98, 161, 72, 169, 76, 182, 120, 124, 205, 246, 11, 218, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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