Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87b1c9612f402883dac760a4269596ff3501830b5b19dc1cc31e0b26dad07b2

Tx prefix hash: a096afac7a343003df5114fd74bbc7e9302d6851bfaa1e6eaed92a2585f8b1a6
Tx public key: 8e202b200a56d233ed17538e342718ac553e3871394633ada8159c9c7e8c98e4
Timestamp: 1718709235 Timestamp [UCT]: 2024-06-18 11:13:55 Age [y:d:h:m:s]: 00:189:15:59:46
Block: 1046859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135743 RingCT/type: yes/0
Extra: 018e202b200a56d233ed17538e342718ac553e3871394633ada8159c9c7e8c98e402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4042444ec3e9fdde1aac82c238ce6f44a2f1d9b3b918fdf7a82eb9f8c4db0e8e 0.600000000000 1516678 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": 1046869, "vin": [ { "gen": { "height": 1046859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4042444ec3e9fdde1aac82c238ce6f44a2f1d9b3b918fdf7a82eb9f8c4db0e8e" } } ], "extra": [ 1, 142, 32, 43, 32, 10, 86, 210, 51, 237, 23, 83, 142, 52, 39, 24, 172, 85, 62, 56, 113, 57, 70, 51, 173, 168, 21, 156, 156, 126, 140, 152, 228, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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