Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d46289b3a402759b2cf44245a5cf2d8a21d18d4fed4dd07fbb6bc5191b7c9a6

Tx prefix hash: bf2721796c69a56836e20e7861bc7941b6f63936d998c1b527374645ed5a5e78
Tx public key: 9dd6afb72c978fee10b5439f0eb0da3198cafcbd1301271a1e696f4f0d05feef
Timestamp: 1702824706 Timestamp [UCT]: 2023-12-17 14:51:46 Age [y:d:h:m:s]: 01:327:19:59:27
Block: 915160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493156 RingCT/type: yes/0
Extra: 019dd6afb72c978fee10b5439f0eb0da3198cafcbd1301271a1e696f4f0d05feef021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27df1fbb8fd02383c80d943f6df5ff61a11b04bdfa046d3b02ea89eca5511234 0.600000000000 1372546 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": 915170, "vin": [ { "gen": { "height": 915160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27df1fbb8fd02383c80d943f6df5ff61a11b04bdfa046d3b02ea89eca5511234" } } ], "extra": [ 1, 157, 214, 175, 183, 44, 151, 143, 238, 16, 181, 67, 159, 14, 176, 218, 49, 152, 202, 252, 189, 19, 1, 39, 26, 30, 105, 111, 79, 13, 5, 254, 239, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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