Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fcd1cdb46136e0de44c0b6ba66f04bc067faba1fb8c8863fe87bb9e8087c5fb

Tx prefix hash: 947f114ad1a132aa119cd2c1cc065320655c51fde711e385af5abcbdcb7eff3c
Tx public key: 923c4e0eb418e54edf5933ff3d048bed9644678bc2235f169a83e9e2c2a59576
Timestamp: 1732676037 Timestamp [UCT]: 2024-11-27 02:53:57 Age [y:d:h:m:s]: 00:111:16:19:35
Block: 1162544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79641 RingCT/type: yes/0
Extra: 01923c4e0eb418e54edf5933ff3d048bed9644678bc2235f169a83e9e2c2a595760211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443b0dde56f68419e8a3c12e76877793db05b30c1c501d13c31cb35098c933a1 0.600000000000 1648201 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": 1162554, "vin": [ { "gen": { "height": 1162544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443b0dde56f68419e8a3c12e76877793db05b30c1c501d13c31cb35098c933a1" } } ], "extra": [ 1, 146, 60, 78, 14, 180, 24, 229, 78, 223, 89, 51, 255, 61, 4, 139, 237, 150, 68, 103, 139, 194, 35, 95, 22, 154, 131, 233, 226, 194, 165, 149, 118, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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