Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5dbab56bd33d62fb2e411d8c2ff992c1881ef27ad4b7c6afd3c1efd4c0f519

Tx prefix hash: d3c5422bcea7dc02b7acf4ab7982b4a065b1cea4d9f6aa805cc0287ba7246785
Tx public key: 886795f5ecf8af6167c2ac26cef936fa8d8e31fec09b977fd0cd13cf88b942c0
Timestamp: 1686411133 Timestamp [UCT]: 2023-06-10 15:32:13 Age [y:d:h:m:s]: 02:151:01:24:17
Block: 779349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 627715 RingCT/type: yes/0
Extra: 01886795f5ecf8af6167c2ac26cef936fa8d8e31fec09b977fd0cd13cf88b942c0021100000001faf35c9c000000000000000000

1 output(s) for total of 1.605807197000 dcy

stealth address amount amount idx
00: a4f06602b771da9f57d0e5478bd822dffd9fae3b76d5ef86e2834326cbb869eb 1.605807197000 1229002 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": 779359, "vin": [ { "gen": { "height": 779349 } } ], "vout": [ { "amount": 1605807197, "target": { "key": "a4f06602b771da9f57d0e5478bd822dffd9fae3b76d5ef86e2834326cbb869eb" } } ], "extra": [ 1, 136, 103, 149, 245, 236, 248, 175, 97, 103, 194, 172, 38, 206, 249, 54, 250, 141, 142, 49, 254, 192, 155, 151, 127, 208, 205, 19, 207, 136, 185, 66, 192, 2, 17, 0, 0, 0, 1, 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