Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d769bb9db555ec88d2888c5a05878467568261fc8b5aa1f9bc9da3d3e02557

Tx prefix hash: 9a435edfe70dbb8a1e49b3dbae8e63cdb307cc388ba476aa2588f79a205c1676
Tx public key: e2214911f541d974bd476ac6f5aa28140f8de131dae7d4e02361f6e217291f18
Timestamp: 1726420266 Timestamp [UCT]: 2024-09-15 17:11:06 Age [y:d:h:m:s]: 00:206:14:36:54
Block: 1110778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147497 RingCT/type: yes/0
Extra: 01e2214911f541d974bd476ac6f5aa28140f8de131dae7d4e02361f6e217291f18021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae3e1626ba8820d1c60e21cd8988c095f4a86076ac912db8b7f6fdda7e3d9c7 0.600000000000 1589509 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": 1110788, "vin": [ { "gen": { "height": 1110778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae3e1626ba8820d1c60e21cd8988c095f4a86076ac912db8b7f6fdda7e3d9c7" } } ], "extra": [ 1, 226, 33, 73, 17, 245, 65, 217, 116, 189, 71, 106, 198, 245, 170, 40, 20, 15, 141, 225, 49, 218, 231, 212, 224, 35, 97, 246, 226, 23, 41, 31, 24, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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