Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c587c5324a94a65fbeb94c421a5ebd332bf1ff494f59946ab5f3b9decffed160

Tx prefix hash: 8887f6078cd6def1f932fe6e801f18b6e6a337f62d7fdaf7e8480dc5101e2c58
Tx public key: 681d7051e39eec7738cc52f45767e1ccbe2542ccd9b62d1bd492f133bbdde2e4
Timestamp: 1725542868 Timestamp [UCT]: 2024-09-05 13:27:48 Age [y:d:h:m:s]: 00:070:05:34:29
Block: 1103517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50210 RingCT/type: yes/0
Extra: 01681d7051e39eec7738cc52f45767e1ccbe2542ccd9b62d1bd492f133bbdde2e402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9057911c38f7aba8ee70c7c1baa362b978f23e6c3a1c9545c79b9c71cdba49f 0.600000000000 1580376 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": 1103527, "vin": [ { "gen": { "height": 1103517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9057911c38f7aba8ee70c7c1baa362b978f23e6c3a1c9545c79b9c71cdba49f" } } ], "extra": [ 1, 104, 29, 112, 81, 227, 158, 236, 119, 56, 204, 82, 244, 87, 103, 225, 204, 190, 37, 66, 204, 217, 182, 45, 27, 212, 146, 241, 51, 187, 221, 226, 228, 2, 17, 0, 0, 0, 6, 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