Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc30bb7f77b4674210562caa6e7c86fd48e49265603e6f0d0d61c8090425755c

Tx prefix hash: d967a50994f825c7cdb5ba6014294abbb37b75aaa55e1a891781134588cf1f22
Tx public key: 4e4d6f58a9fc61ef54934308c2edfb63b38cfc14672e273f24a544e40bcc4245
Timestamp: 1697454651 Timestamp [UCT]: 2023-10-16 11:10:51 Age [y:d:h:m:s]: 01:030:05:20:01
Block: 870839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282819 RingCT/type: yes/0
Extra: 014e4d6f58a9fc61ef54934308c2edfb63b38cfc14672e273f24a544e40bcc4245021100000001faf35c9c000000000000000000

1 output(s) for total of 0.799093932000 dcy

stealth address amount amount idx
00: 790ea19c548c47d461ce268582f3f9cca801c9039d8309d9b1fcea5e7ed67310 0.799093932000 1325770 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": 870849, "vin": [ { "gen": { "height": 870839 } } ], "vout": [ { "amount": 799093932, "target": { "key": "790ea19c548c47d461ce268582f3f9cca801c9039d8309d9b1fcea5e7ed67310" } } ], "extra": [ 1, 78, 77, 111, 88, 169, 252, 97, 239, 84, 147, 67, 8, 194, 237, 251, 99, 179, 140, 252, 20, 103, 46, 39, 63, 36, 165, 68, 228, 11, 204, 66, 69, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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