Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d08e76a4e6c96e8fd69eff4ecaab6d36f8fac3c664ed0157a82526d58c924e

Tx prefix hash: 6d309b4ab887143c4befeeef44a786ebb8f41bee85a0718795d109a91d17df04
Tx public key: c875e6e0b54725614ad7c6f1e0a64f21bc7747620ddc656ca5eb123d85f94d98
Timestamp: 1710590743 Timestamp [UCT]: 2024-03-16 12:05:43 Age [y:d:h:m:s]: 01:242:16:49:38
Block: 979567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432150 RingCT/type: yes/0
Extra: 01c875e6e0b54725614ad7c6f1e0a64f21bc7747620ddc656ca5eb123d85f94d980211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41e018184b8c46b1cedc465425c6460033888e3cdb17451e882b4fa2d04eacd9 0.600000000000 1439604 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": 979577, "vin": [ { "gen": { "height": 979567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41e018184b8c46b1cedc465425c6460033888e3cdb17451e882b4fa2d04eacd9" } } ], "extra": [ 1, 200, 117, 230, 224, 181, 71, 37, 97, 74, 215, 198, 241, 224, 166, 79, 33, 188, 119, 71, 98, 13, 220, 101, 108, 165, 235, 18, 61, 133, 249, 77, 152, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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