Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d443d04e03116542ca0aa99efc3bcd6d69920146cafb0bb8e98c302c18d3fddb

Tx prefix hash: 4485332db52e1ec32873ee0cc3923b3eaa592a18b1a2685558c38d68894e8790
Tx public key: 6a41184002675fda4bbcac1d3591cb0e3abd09e095380c46965cd3275a18e4f0
Timestamp: 1702940222 Timestamp [UCT]: 2023-12-18 22:57:02 Age [y:d:h:m:s]: 01:148:02:36:34
Block: 916123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367005 RingCT/type: yes/0
Extra: 016a41184002675fda4bbcac1d3591cb0e3abd09e095380c46965cd3275a18e4f0021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4df63083e4d22ea0170e22a303a5ab4ab2436ec4f2de826d950770ec77beda0 0.600000000000 1373601 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": 916133, "vin": [ { "gen": { "height": 916123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4df63083e4d22ea0170e22a303a5ab4ab2436ec4f2de826d950770ec77beda0" } } ], "extra": [ 1, 106, 65, 24, 64, 2, 103, 95, 218, 75, 188, 172, 29, 53, 145, 203, 14, 58, 189, 9, 224, 149, 56, 12, 70, 150, 92, 211, 39, 90, 24, 228, 240, 2, 17, 0, 0, 0, 9, 230, 210, 127, 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