Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7ef9cb2cb2ea6c7548ca16b0e526c1260d6735af97a51f2bfa3f12a9261553a

Tx prefix hash: 0a4a75acdfffab5ca8c09d10c00b15631c798666f8611df7e426beeb8730f966
Tx public key: f1dc7f96c2a1e179d37c35b12a61a69395a048d31e55d0fcb19369a926db3bf2
Timestamp: 1657173024 Timestamp [UCT]: 2022-07-07 05:50:24 Age [y:d:h:m:s]: 03:116:16:27:27
Block: 538393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863113 RingCT/type: yes/0
Extra: 01f1dc7f96c2a1e179d37c35b12a61a69395a048d31e55d0fcb19369a926db3bf20211000000014da16a3a000000000000000000

1 output(s) for total of 10.094403083000 dcy

stealth address amount amount idx
00: 18370689617b75f08840d09b60c6828daa78e0fb84f42b8ae940e667118ad6e1 10.094403083000 968388 of 0

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": 538403, "vin": [ { "gen": { "height": 538393 } } ], "vout": [ { "amount": 10094403083, "target": { "key": "18370689617b75f08840d09b60c6828daa78e0fb84f42b8ae940e667118ad6e1" } } ], "extra": [ 1, 241, 220, 127, 150, 194, 161, 225, 121, 211, 124, 53, 177, 42, 97, 166, 147, 149, 160, 72, 211, 30, 85, 208, 252, 177, 147, 105, 169, 38, 219, 59, 242, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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