Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986fda17714b81d279140e44cf6cb26f3c62251378bfc60188231cda3a7f8812

Tx prefix hash: 1dcda0bae7225b29baca3db44fa63dccf78780a7e3d8eb77697eccc4dcb47d18
Tx public key: 386ada0a7a4bcc403ababd352b73b36c327c6f1080ae87e098da8dd8fffce8a9
Timestamp: 1722136878 Timestamp [UCT]: 2024-07-28 03:21:18 Age [y:d:h:m:s]: 00:256:10:39:42
Block: 1075273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183190 RingCT/type: yes/0
Extra: 01386ada0a7a4bcc403ababd352b73b36c327c6f1080ae87e098da8dd8fffce8a902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b197796acfd5e66ba5a7013d7f9c856581aad8a3ea133859903b1a71a59f3e34 0.600000000000 1547798 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": 1075283, "vin": [ { "gen": { "height": 1075273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b197796acfd5e66ba5a7013d7f9c856581aad8a3ea133859903b1a71a59f3e34" } } ], "extra": [ 1, 56, 106, 218, 10, 122, 75, 204, 64, 58, 186, 189, 53, 43, 115, 179, 108, 50, 124, 111, 16, 128, 174, 135, 224, 152, 218, 141, 216, 255, 252, 232, 169, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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