Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7129d8c9dbfba028ec39b524e2f4b18283ea1e1f0714506ff6a9b5e3fea3cd21

Tx prefix hash: 7cba956e50489acd73a7e270fbad8e434cfab7523ec5f1466bbcee3d25af3b7b
Tx public key: 0eb86ecd1cd85669e0e1c387bccf944125e0d6d53b4d788ee5ef82b4790eb2e5
Timestamp: 1728200466 Timestamp [UCT]: 2024-10-06 07:41:06 Age [y:d:h:m:s]: 00:179:16:51:12
Block: 1125543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128230 RingCT/type: yes/0
Extra: 010eb86ecd1cd85669e0e1c387bccf944125e0d6d53b4d788ee5ef82b4790eb2e502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f5ffa3e3cb25d6b6ff740e8e11e64288dc6a1a1c8a0c3aa522fcdbe41e2cf7b 0.600000000000 1608294 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": 1125553, "vin": [ { "gen": { "height": 1125543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f5ffa3e3cb25d6b6ff740e8e11e64288dc6a1a1c8a0c3aa522fcdbe41e2cf7b" } } ], "extra": [ 1, 14, 184, 110, 205, 28, 216, 86, 105, 224, 225, 195, 135, 188, 207, 148, 65, 37, 224, 214, 213, 59, 77, 120, 142, 229, 239, 130, 180, 121, 14, 178, 229, 2, 17, 0, 0, 0, 1, 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