Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53ef94a227c1452cf838b644e0ea0ee57e41115aa561774f4a477f2a2a2f50cd

Tx prefix hash: b99f817778dcbb1e6bc31bbcd747e83762d8155f2f43ccb443b04d874867472f
Tx public key: f8a522ad4e934ec08d7e372133c0af0173e5eae02be678e55fd2203a2864629e
Timestamp: 1634775524 Timestamp [UCT]: 2021-10-21 00:18:44 Age [y:d:h:m:s]: 03:221:04:01:43
Block: 357104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 936134 RingCT/type: yes/0
Extra: 01f8a522ad4e934ec08d7e372133c0af0173e5eae02be678e55fd2203a2864629e02110000000337cb3088000000000000000000

1 output(s) for total of 40.250068171000 dcy

stealth address amount amount idx
00: fe4c34b20dfd466531ba07d08bb379540e3b1f71169922a1d190edf6b2eb16b5 40.250068171000 728310 of 0

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": 357114, "vin": [ { "gen": { "height": 357104 } } ], "vout": [ { "amount": 40250068171, "target": { "key": "fe4c34b20dfd466531ba07d08bb379540e3b1f71169922a1d190edf6b2eb16b5" } } ], "extra": [ 1, 248, 165, 34, 173, 78, 147, 78, 192, 141, 126, 55, 33, 51, 192, 175, 1, 115, 229, 234, 224, 43, 230, 120, 229, 95, 210, 32, 58, 40, 100, 98, 158, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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