Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1dcb7b8aedb8aa061ab582437f773e4dda59eaba816690a3ecfdc13e1560006

Tx prefix hash: 30f52bab0da4718043f3e0cbbc62f7fa5dbb87d1e92e6589ded887cef81f03e9
Tx public key: a91a9fb395ac4d64c8c12348670a0da089167fc400bf74c4ff2100026f62d78b
Timestamp: 1711822964 Timestamp [UCT]: 2024-03-30 18:22:44 Age [y:d:h:m:s]: 00:331:11:41:16
Block: 989786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236950 RingCT/type: yes/0
Extra: 01a91a9fb395ac4d64c8c12348670a0da089167fc400bf74c4ff2100026f62d78b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c54abd7dff6cf6cb946cfbb2a8b65f7ef8f23ab6264e54459cea63ce5c364db3 0.600000000000 1450104 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": 989796, "vin": [ { "gen": { "height": 989786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c54abd7dff6cf6cb946cfbb2a8b65f7ef8f23ab6264e54459cea63ce5c364db3" } } ], "extra": [ 1, 169, 26, 159, 179, 149, 172, 77, 100, 200, 193, 35, 72, 103, 10, 13, 160, 137, 22, 127, 196, 0, 191, 116, 196, 255, 33, 0, 2, 111, 98, 215, 139, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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