Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30165b626c138f6cdb724cffa1812fcf52dd52eed061b94a09f75c4bcbaa7631

Tx prefix hash: 1ce54aa0a0f292549f62b4a540b9a1b066a540c3726d1a0ebe04fe4543cfdc7f
Tx public key: 9c38cf093918ccd1194deb939058220de56c54e4a83369f7da39b7aef4a542bc
Timestamp: 1729724606 Timestamp [UCT]: 2024-10-23 23:03:26 Age [y:d:h:m:s]: 00:183:15:07:09
Block: 1138148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131058 RingCT/type: yes/0
Extra: 019c38cf093918ccd1194deb939058220de56c54e4a83369f7da39b7aef4a542bc0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b1d603e88b57710382fdf4379c9bb2bcff9f455b819f43a85a02f0c43769e0a 0.600000000000 1621761 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": 1138158, "vin": [ { "gen": { "height": 1138148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b1d603e88b57710382fdf4379c9bb2bcff9f455b819f43a85a02f0c43769e0a" } } ], "extra": [ 1, 156, 56, 207, 9, 57, 24, 204, 209, 25, 77, 235, 147, 144, 88, 34, 13, 229, 108, 84, 228, 168, 51, 105, 247, 218, 57, 183, 174, 244, 165, 66, 188, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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