Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b838c912c27c202f6dcc45ec8b8c69b32c9ff3de9eeb1a6bd7f8c8684e4750a3

Tx prefix hash: 8e964746e787604bb624f2b040f199b6243467b578d07d422b36705d96ec6e7d
Tx public key: 350eeba74fc674641d54a1aff95177e37938c8a7e19c299d18db720abcc0b079
Timestamp: 1734274888 Timestamp [UCT]: 2024-12-15 15:01:28 Age [y:d:h:m:s]: 00:104:05:47:18
Block: 1175813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74273 RingCT/type: yes/0
Extra: 01350eeba74fc674641d54a1aff95177e37938c8a7e19c299d18db720abcc0b0790211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e545014d621bc4e1f8229a92e6e51a9cb53e29d636a55f4ca1270d8eb7ce4b6 0.600000000000 1662138 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": 1175823, "vin": [ { "gen": { "height": 1175813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e545014d621bc4e1f8229a92e6e51a9cb53e29d636a55f4ca1270d8eb7ce4b6" } } ], "extra": [ 1, 53, 14, 235, 167, 79, 198, 116, 100, 29, 84, 161, 175, 249, 81, 119, 227, 121, 56, 200, 167, 225, 156, 41, 157, 24, 219, 114, 10, 188, 192, 176, 121, 2, 17, 0, 0, 0, 6, 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